Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update MD-F comparison to point to OpenFAST/dev #232

Open
wants to merge 134 commits into
base: dev
Choose a base branch
from

Conversation

RyanDavies19
Copy link
Collaborator

OpenFAST/dev now has a more robust suite of regression tests that should capture most of MoorDyn's capabilities including 6 DOF dynamics and cable. Our checking of things should be against the dev branch for the time being until it gets merged into OpenFAST/main. This might break the MD-F tests for #231.

Corresponding OpenFAST PR: OpenFAST/openfast#2294

@RyanDavies19
Copy link
Collaborator Author

RyanDavies19 commented Jul 9, 2024

@sanguinariojoe okay we now have test artifacts with plots of channels and error thresholds so we can see what is broken. As for why those tests don't line up, that will take further investigation. In the mean-time this is ready to be merged.

@RyanDavies19 RyanDavies19 changed the title WIP: Update MD-F comparison to point to OpenFAST/dev Update MD-F comparison to point to OpenFAST/dev Jul 9, 2024
@RyanDavies19
Copy link
Collaborator Author

@AlexWKinley and @sanguinariojoe, not sure if either of you have a rush for exact kinematics but what's in MD-C at the moment isn't entirely right. Once OpenFAST/openfast#2334 is merged, a corresponding update needs to be made on the MD-C side to the body and rod kinematics (adding centripetal moments in addition to the centripetal forces from #231). That will be a more correct approach to 6 DOF kinematics.

After that is done, tests here should agree with the exception of md_lineFail. md_lineFail will be fixed when I get around to updating our line failures

@sanguinariojoe
Copy link
Collaborator

Everything good on my end, no need to rush. I am busy with some other interesting stuff for MoorDyn! :-p

@AlexWKinley
Copy link
Contributor

Similarly, no rush from my end. (Although I suspect that exactly correct kinematics in 6dof are still more complicated than any of our numerical models have accounted for). I'm busy with other work for the moment. I do super appreciate the work that's been happening here in terms of checking agreement between the two MoorDyn implementations.

@sanguinariojoe
Copy link
Collaborator

@AlexWKinley and @sanguinariojoe, not sure if either of you have a rush for exact kinematics but what's in MD-C at the moment isn't entirely right. Once OpenFAST/openfast#2334 is merged, a corresponding update needs to be made on the MD-C side to the body and rod kinematics (adding centripetal moments in addition to the centripetal forces from #231). That will be a more correct approach to 6 DOF kinematics.

After that is done, tests here should agree with the exception of md_lineFail. md_lineFail will be fixed when I get around to updating our line failures

Hey! How are you doing with this? Are you preparing a PR?

@RyanDavies19
Copy link
Collaborator Author

Hi @sanguinariojoe, I haven't had much time recently to take a stab at this, and I probably won't for the next couple weeks. I've blocked out some time at the end of October/Early November to work on this. Aside from updating the line failure capability on this side, there are a couple of areas I suspect need to be aligned Namely hydrodynamics of rods, submergence of lines, and rigid body kinematics.

On a more logistical note, I will try to keep the MD-F regression tests to the core MoorDyn capabilities. That way as new auxiliary features are added on either side, they won't cause the tests the fail while we still maintain the same performance with the core things (6 DOF kinematics, line modeling, etc.)

@sanguinariojoe
Copy link
Collaborator

OK, as long as you have it planned I just wait

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants